-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group possible backend share configurations under same environment #117
Group possible backend share configurations under same environment #117
Conversation
5a9628f
to
b84556a
Compare
b84556a
to
ae84f60
Compare
I have another branch(group-backend-shares2) which reduces the complexity of changes from test-info.yml.j2 by defining the strategies within global settings.yml. |
ae84f60
to
681a83b
Compare
/retest centos-ci/gpfs.scale |
Notes: Shares created cephfs: cephmgr: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. ACK
With [1] all possible share configurations are grouped after their respective backend file system. So those duplicate entries can be removed reducing the number of jobs in the matrix. [1] samba-in-kubernetes/sit-environment#117
With [1] suffix 'vfs' is irrelevant in 'cephfs.mgr.vfs' as multiple share configurations are included within mgr variant. [1] samba-in-kubernetes/sit-environment#117
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the meaning of variant and method (or strategy) is a bit mixed. Why do we need variant if we already have another list that contains all the variants we want to use ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the meaning of variant and method (or strategy) is a bit mixed. Why do we need variant if we already have another list that contains all the variants we want to use ?
I intent to change the meaning of variant to indicate how(or who) Samba and/or CTDB configurations are handled during cluster setup. With this we will have just two variants namely, default
(independent setup style) and mgr
(using ceph mgr module). Each of these variants can have different methods through which shares are configured for client access.
This means that the variant only makes sense for the ceph backend. All other backends won't have variants, which is a bit weird. I think that we should move the definition of backends inside settings.yml (see #119). Then we could easily extend the definition like this (just a possible way, not thought much about it): backends:
cephfs:
provider: mgr
settings:
<optional mgr specific options>
shares:
kclient:
<optional kclient specific options>
vfs:
<optional vfs specific options> This way we could easily create more than one backend, with multiple shares, in a single configuration (additional work required to avoid using the same devices, but that's another problem). In any case, this is not related to this patch. We can discuss this in #119. |
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
681a83b
to
b5b3cf3
Compare
I have considered
Sure. For now I've updated to include the suggestion to use only |
With samba-in-kubernetes/sit-environment#117, 'variant' no longer indicates the method through which a particular share is configured for client access. Instead determine the need for VFS specific flapping file using the share name itself. Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
With samba-in-kubernetes/sit-environment#117, 'variant' no longer indicates the method through which a particular share is configured for client access. Instead determine the need for VFS specific flapping file using the share name itself. Signed-off-by: Anoop C S <anoopcs@cryptolab.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
With [1] all possible share configurations are grouped after their respective backend file system. So those duplicate entries can be removed reducing the number of jobs in the matrix. [1] samba-in-kubernetes/sit-environment#117
With [1] suffix 'vfs' is irrelevant in 'cephfs.mgr.vfs' as multiple share configurations are included within mgr variant. [1] samba-in-kubernetes/sit-environment#117
With [1] all possible share configurations are grouped after their respective backend file system. So those duplicate entries can be removed reducing the number of jobs in the matrix. [1] samba-in-kubernetes/sit-environment#117
With [1] suffix 'vfs' is irrelevant in 'cephfs.mgr.vfs' as multiple share configurations are included within mgr variant. [1] samba-in-kubernetes/sit-environment#117
Key considerations:
methods
field to indicate how variations of each share section are to be configured within smb.conf.scale
variant configuration is always based on vfs. Thus we skip iterating over available methods.fixes #101